chore: bump rust-dashcore rev to 95a3c8ff04d75d7abe324db4af01e8521092aff9#3955
chore: bump rust-dashcore rev to 95a3c8ff04d75d7abe324db4af01e8521092aff9#3955ZocoLini wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdates the git ChangesDashCore Revision Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
✅ Review complete (commit bc9c65b) |
thepastaclaw
left a comment
There was a problem hiding this comment.
Code Review
Convergent blocking finding from both agents: Cargo.lock was not regenerated after bumping the rust-dashcore git rev in Cargo.toml. CI uses --locked, so the manifest/lockfile mismatch will break builds and prevent consumers from actually receiving the upstream Swift-SDK panic fix this PR advertises.
🔴 1 blocking
1 additional finding(s) omitted (not in diff).
🤖 Prompt for all review comments with AI agents
These findings are from an automated code review. Verify each finding against the current code and only fix it if needed.
In `Cargo.lock`:
- [BLOCKING] Cargo.lock:1640: Cargo.lock not regenerated for new rust-dashcore rev
Cargo.toml lines 53–60 pin all 8 rust-dashcore workspace deps (dashcore, dash-network-seeds, dash-spv, key-wallet, key-wallet-ffi, key-wallet-manager, dash-network, dashcore-rpc) to rev 95a3c8ff04d75d7abe324db4af01e8521092aff9, but Cargo.lock still records each of those crates from the prior rev 5c0113e7901551450f6063023eec4be95beeb6b9 (verified at lines 1640, 1651, 1728, 1757, 1783, …). The project's Rust CI invokes Cargo with --locked, so the manifest/lockfile inconsistency will fail the build immediately. More importantly, until the lockfile is regenerated, the stated fix for swift-sdk panics is not actually delivered to anyone building via --locked or to the iOS xcframework build pipeline that consumes key-wallet-ffi / dash-spv through rs-unified-sdk-ffi. Regenerate the lockfile (e.g. `cargo update -p dashcore -p dash-network-seeds -p dash-spv -p key-wallet -p key-wallet-ffi -p key-wallet-manager -p dash-network -p dashcore-rpc`) and commit the resulting Cargo.lock changes alongside the Cargo.toml bump.
277f6f1 to
bc9c65b
Compare
thepastaclaw
left a comment
There was a problem hiding this comment.
Code Review
The prior Cargo.lock mismatch is FIXED: Cargo.toml and all rust-dashcore-sourced Cargo.lock entries now point to rev 95a3c8ff04d75d7abe324db4af01e8521092aff9, and the old 5c0113e7901551450f6063023eec4be95beeb6b9 rev is no longer present in the checked manifests or lockfile. cargo metadata --locked --no-deps --format-version 1 succeeds, confirming the lockfile is internally consistent with the current workspace manifests. No agent or CodeRabbit findings remain to carry forward.
With this rust-dashcore bump we introduce a fix for some swift sdk panics under specific conditions
Checklist:
For repository code-owners and collaborators only
Summary by CodeRabbit
Release Notes